Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum


  

PreviousPrevious NextNext


~Sean Asaboosilylen 9.Apr.03 03:28 PM a Web browser
Domino Server 6.0.1 Windows 2000


I upgraded two enterprise 5.0.12 servers (clustered) to 6.01 enterprise on Saturday evening. Both servers are running Windows 2000, sp2. I previously upgraded a handful of application and admin servers to 6.0, then from 6.0 to 6.01, and had no issues. I followed all of the upgrade steps in the admin help and redbooks and read all release notes.

Monday morning, I began getting calls from users who were getting "invalid or nonexistent document" errors when replicating. Some were receiving mail to their All Documents view but not to their inboxes. I have had occasional experience with corruption before, and was able to repair each database as it was reported by running fixup and, if necessary, refreshing the design, but I was alarmed by the number of corruption reports immediately following an upgrade. When the reports kept coming in yesterday, I opened an incident with Lotus. Lotus says this is not a known issue with the upgrade, and recommended running fixup -j against my whole mail directory. I decided to do that after hours in case of performance issues.

Yesterday afternoon, the mail server started crashing. It crashed twice in an hour, so I opened another, higher severity incident with Lotus. At first, I was again told that there were no known issues associated with the upgrade, but I later got a call back saying that my NSD matched a "known issue" that had a hotfix. At 10pm last night, I was advised that the hotfix had actually only been written for the 390 platform, and that it would have to be ported to Windows for me, as I was the first person to report the issue on Windows.

Last night, I ran fixup -j on my entire mail directory. Logs of the time period during the fixup reveal that several hundred mail files had corrupt documents. I then took down the mail servers and ran ncompact, nfixup, and nupdall on all system databases.

This morning, I've received more calls regarding corrupt databases, even after running the fixup last night - they appear to be corrupting again. Additionally, people's unread marks are fluctuating between read and unread, and in a few cases, people's mail has "reappeared" in their inboxes after several months in folders. The server has already crashed again once.

I have been told that the hotfix will be available later today. Hopefully that will alleviate the crashing. However, I am getting very little useful information or advice regarding the recurring corruption and unread marks issues. The people working on the hotfix seem to think the crashes and corruption are unrelated, but both started with the upgrade, so I think they must be.

I have asked if I should revert back to 5, but Lotus doesn't recommend it, because they said they don't think the corruption would be repaired. I've searched this forum and it looks like most people have had good success with the upgrade. I wanted to post my experience in case anyone else out there runs into the same issues I've had, because they seem to be fairly new, even to Lotus.

If anyone has advice on the corruption issues, I'd love to hear it. Thanks!






Serious issues with Domino 6.01 upg... (~Sean Asaboosil... 9.Apr.03)
. . You say you ran NCompact? What swit... (~Dan Elhipister... 9.Apr.03)
. . . . RE: You say you ran NCompact? What ... (~Sean Asaboosil... 9.Apr.03)
. . . . . . Make sure you run "NCompact -C" whi... (~Dan Elhipister... 9.Apr.03)
. . . . . . . . RE: Make sure you run "NCompact -C"... (~Sean Asaboosil... 9.Apr.03)
. . RE: Serious issues with Domino 6.01... (~Sven Fezvelute... 9.Apr.03)
. . . . RE: Serious issues with Domino 6.01... (~Olga Opfooster... 10.Apr.03)
. . . . . . RE: Serious issues with Domino 6.01... (~Sean Asaboosil... 10.Apr.03)
. . . . . . . . RE: Serious issues with Domino 6.01... (~Olga Opfooster... 10.Apr.03)
. . RE: Serious issues with Domino 6.01... (~Fred Dwoveluth... 11.Apr.03)
. . . . RE: Serious issues with Domino 6.01... (~Fred Dwoveluth... 11.Apr.03)
. . . . . . Did you also run Compact -C (Copy s... (~Dan Elhipister... 11.Apr.03)
. . . . . . . . RE: Did you also run Compact -C (Co... (~Fred Dwoveluth... 15.Apr.03)
. . . . . . . . . . This fixed it for us! (~Jennifer Kikim... 1.May.03)
. . . . . . . . . . . . Re This fixed it for us! (~Delores Xanres... 13.May.03)
. . RE: Serious issues with Domino 6.01... (~Lily Minkither... 11.Apr.03)
. . . . Serious issues with Domino 6.01 upg... (~Sean Renulitfl... 18.Jun.03)
. . . . . . RE: Serious issues with Domino 6.01... (~Denise Elrevit... 25.Sep.03)
. . Here's the skinny as related to us ... (~George Bubresa... 22.Apr.03)
. . . . FIXED. Converting ODS to 43. (~George Bubresa... 23.Apr.03)
. . RE: Serious issues with Domino 6.01... (~Nicole Lopfana... 10.Apr.03)
. . . . RE: Serious issues with Domino 6.01... (~Sean Asaboosil... 10.Apr.03)
. . . . . . RE: Serious issues with Domino 6.01... (~Chloe Fezreplo... 11.Apr.03)
. . . . . . . . RE: Serious issues with Domino 6.01... (~Sean Asaboosil... 11.Apr.03)
. . . . . . . . . . RE: Serious issues with Domino 6.01... (~Olga Opfooster... 11.Apr.03)
. . . . . . . . . . . . Yes, plse post your findings Debra.... (~Miriam Refooma... 11.Apr.03)
. . . . . . . . . . . . . . Looks like the downgrade did it (~Sean Asaboosil... 11.Apr.03)
. . . . . . . . . . . . . . . . RE: Looks like the downgrade did it... (~Keiko Lopweste... 14.Apr.03)
. . . . . . . . . . . . . . . . . . Solution for us! Looks like the dow... (~Lily Zenweburl... 15.Apr.03)
. . . . . . . . . . . . . . . . . . . . Sorry, It did not works for us eom>... (~Kim Dworesache... 15.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . Server Upgrade (~Joan Chukropul... 17.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Fred Dwoveluth... 18.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Olga Opfooster... 18.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Sean Asaboosil... 18.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Fred Dwoveluth... 19.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Wei Ekluburgon... 19.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Fred Dwoveluth... 20.Apr.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Ben Kiponemanl... 14.May.03)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RE: Server Upgrade (~Yoshi Refreeve... 15.Jul.03)
. . . . RE: Serious issues with Domino 6.01... (~John Zenfooche... 22.Apr.03)
. . . . . . RE: Serious issues with Domino 6.01... (~Sven Fezboosig... 10.Jun.03)
. . . . . . . . RE: Serious issues with Domino 6.01... (~Fred Dwoveluth... 19.Jun.03)





  Document options
Print this pagePrint this page

 Search this forum

  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Category
Platform
Release
Advanced search

 RSS feedsRSS
All forum posts RSS
All main topics RSS